Skip to content

Bugfix/cstackex 327-Concurrent iSCSI VM deployment fails intermittently: post-clone LUN resize returns 404 - #118

Open
sp16743 wants to merge 3 commits into
mainfrom
bugfix/CSTACKEX-327
Open

sp16743 wants to merge 3 commits into
mainfrom
bugfix/CSTACKEX-327

Conversation

@sp16743

@sp16743 sp16743 commented Oct 9, 2026

Copy link
Copy Markdown
Collaborator

Description

After an iSCSI template clone, CloudStack grows the new LUN when the service offering disk is larger than the template. ONTAP returns the LUN UUID from the clone, but the immediate resize PATCH /api/storage/luns/{uuid} can return HTTP 404 (entry doesn't exist, target uuid) before that LUN is visible.

resizeCloudStackVolume now retries only that PATCH, using the same UUID. A 404 is retried for up to 30 attempts, one second apart. Any other error fails on the first attempt.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

Before the fix:
Screenshot 2026-09-30 at 3 57 53 PM

How Has This Been Tested?

1 VM Created
Screenshot 2026-10-09 at 9 55 57 PM
10 VMs created Concurrently:
Screenshot 2026-10-09 at 9 53 48 PM
Screenshot 2026-10-09 at 9 54 00 PM
5 VMs created Concurrently:
Screenshot 2026-10-09 at 7 57 23 PM
20 VMs Created Concurrently:
Screenshot 2026-10-09 at 8 07 28 PM
Screenshot 2026-10-09 at 8 07 38 PM
Screenshot 2026-10-09 at 8 07 52 PM

With data disk:
1 VM:
Screenshot 2026-10-09 at 10 10 43 PM
5 VMs Concurrently:
Screenshot 2026-10-09 at 10 12 10 PM
10 VMs Concurrently:
Screenshot 2026-10-09 at 10 14 17 PM
20VMs Concurrently:
Screenshot 2026-10-09 at 10 17 53 PM
Screenshot 2026-10-09 at 10 18 02 PM

How did you try to break this feature and the system with this change?

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown

🔴 Test Coverage Grade: D — Marginal

Metric Value
Line coverage 24.82%
Branch coverage 18.97%

Grade Scale

Grade Line Coverage Meaning
🟢 A ≥ 80% Excellent - this code sleeps well at night 😴
🟡 B 60-79% Good - almost there, don't stop now 😉
🟠 C 40-59% Acceptable - your code is wearing a seatbelt, but no airbags 😬
🔴 D 20-39% Marginal - boldly shipping where no test has gone before 🖖
⛔ F < 20% Failing - tests? what tests? 🔥

Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant